User initiated rule-based restrictions on messaging applications

ABSTRACT

A method, system and computer program product are disclosed for user initiated rule based restrictions on sending messages from a sender to a receiver in a communications network. The receiver establishes a set of rules for the sender that allows the sender a limited number of defined messages events with the receiver. The defined message events may be messages or message sessions. When the sender attempts to send a message to the receiver, it is determined whether a message session currently exists between the sender and the receiver. If a current session exists, the rules set by the receiver are used to determine if the message is allowed to be sent to the receiver. If a session does not currently exist, the rules are used to determine whether a new session is allowed. If a new message session is allowed, a new session is established, and the message is sent to the receiver during the new session.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of copending U.S. patent applicationSer. No. 12/818,589, filed Jun. 18, 2010, the disclosure of which ishereby incorporated herein by reference in its entirety.

BACKGROUND OF THE INVENTION

The present invention generally relates to messaging applications, suchas text messaging and instant messaging. More specifically, theinvention relates to user initiated rule based restrictions on the useof messaging applications.

BACKGROUND ART

A wide range of communication technologies are available and in commonuse that enable communications by voice, email or the like. Today,communications may be commonly performed using various messagingservices such as Instant Messaging (IM), Short Message Service (SMS),Multimedia Messaging Service (MMS), and Enhanced Message Service (EMS).

IM allows a user to send and receive messages nearly instantaneouslywith other IM service users over a network or collection of networks,such as the Internet. A computer connected to the Internet can accessthe IM service using a client application. The client application can beimplemented as a local client or a browser based client. A local clientis a program which is stored on the computer and provides an interfaceallowing a user to access the IM service. A browser based client basedclient is a program which is generally provided by a web server. Theinterface loaded from the server allows the user to access the IMservice. IM services are provided to an IM service domain which iscomprised of entities having an account with the IM service.

To use IM, a user establishes an account by providing accountinformation including a user identifier, a password, and a list ofmessenger contacts. Subsequent login to the service requires the user toprovide the user identifier and password. Upon confirmation of the logininformation with the user's account information, the particular client(either local or browser based) displays an interface indicating theuser's presence, messenger contact list and the presence of eachcontact. Presence is a status indication of whether an entity is onlineor offline, and can also be used to indicate a state of “busy”, “away”,“out to lunch”, or other states. If the entity, such as the user or acontact on the user's messenger contact list, is logged in to amessenger server within the IM service, then the entity's presence is“online”. Otherwise, the presence for the entity is “offline”.

The user may select a contact from the messenger contact list displayedin an IM interface to initiate a conversation. Once selected, the clientapplication associate with each conversation member provides aconversation window. In some IM systems, the client applicationsassociated with a conversation receive direct contact information foreach other to provide direct communication between them. In other IMservices, the client applications for each conversation member areconnected to each other through the IM system. When a conversationmember sends a message, the IM system receives the message, finds therecipient member's computer location and routes the message to theparticular computer. Instant messaging (IM) services are typicallylimited to interactions between users of a specific messagingservice/network, although some services offer inter-connectivity betweenservices/networks.

SMS, also referred to as text messaging, is a service that enables usersto exchange short text messages over a communication network. SMS isavailable on most mobile phones, some personal digital assistants andcomputers (typically via internet sites providing SMS services). Themost common application of SMS is person-to-person messaging, but textmessages can also be used to interact with automated systems, such asordering products and services for mobile phones, participating incontests, receiving news alerts, receiving calendar alerts, voting inpopular TV shows, and receiving weather or coastal warning alerts orother warnings.

SMS is a store and forward service, i.e., text messages are not sentdirectly from sender to recipient, but always via a Short MessageService Center (SMSC). The SMSC handles and manages the text messages byrouting text messages between mobile users via each device's MobileStation International Subscriber Directory Number (MSISDN).

With IM and SMS, and other messaging applications, becoming more andmore common, users may receive many unwanted messages and be bombardedwith large numbers of messages, both of which may be significantnuisances for the users. Realizing this problem, people have come upwith ways to completely block some unwanted messages. But, it may not bepossible or desirable to block certain users/messages since some of themessages sent by a user might be useful. But it being a free or easy touse option, people do misuse messaging services in a sense that theymight send messages unnecessarily. There needs to be a way in whichpeople can be restricted to send only useful and essential messages.There may be a need to restrict messages from certain users, so thatthey use the messaging services more efficiently, and only when needed.

BRIEF SUMMARY

Embodiments of the invention provide a method, system and computerprogram product for user initiated rule based restrictions on sendingmessages from a sender to a receiver. In one embodiment, the inventionprovides a method comprising the receiver establishing a set of rulesfor the sender and storing the set of rules in a datastore, said set ofrules including allowing the sender a limited number of defined messagesevents with the receiver. The method further comprises the senderattempting to send a message to the receiver, and determining whether amessage session currently exists between the sender and the receiver.

If a message session currently exists between the sender and thereceiver, the set of rules established by the receiver are accessed todetermine if the sender is allowed to send the message to the receiverduring said message session currently existing. If the sender is allowedto send said message during the message session currently existing, themessage is sent to the receiver.

In this embodiment, if a message session does not currently existbetween the sender and the receiver, the set of rules established by thereceiver are used to determine whether a new message session is allowedbetween the sender and the receiver. If a new message session isallowed, a new message session is established between the sender and thereceiver, and the message is sent to the receiver during the new messagesession.

In one embodiment, the defined message events are message sessions, andthe sender is allowed a limited number of message sessions with thereceiver. In one embodiment, the defined message events are messages,and the sender is allowed to send a limited number of messages to thereceiver.

In one embodiment, determining if the sender is allowed to send themessage to the receiver during said message session currently existingincludes determining if the message session currently existing has timedout. In an embodiment, determining if the sender is allowed to send themessage to the receiver during the message session currently existingincludes determining whether the receiver allows the message to be sentto the receiver in the message session currently existing even if themessage session currently existing has timed out.

In an embodiment, the set of rules established by the receiver includesa limit on the number of message sessions allowed between the sender andthe receiver during a defined time period. In one embodiment,determining whether a new message session is allowed includesdetermining whether this limit on the number of message sessions hasbeen reached. In one embodiment, if this limit has been reached, analert is sent to the sender to inform the sender that the limit has beenreached, and the message is blocked from the receiver.

In one embodiment, the set of rules established by the sender includesan alert threshold number, and determining whether a new message sessionis allowed includes determining whether the number of message sessionsbetween the sender and the receiver has reached this alert thresholdnumber. In an embodiment, if this alert threshold has been reached, thesender is alerted that the threshold has been reached.

In one embodiment, a count is kept of the number of message sessionsbetween the sender and the receiver during said defined time period. Inan embodiment, selected ones of the message sessions between the senderand the receiver are not included in this count. The messages sessionsnot included in this count may be determined by criteria set by thereceiver.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows an architecture illustrating principals of embodiments ofthe invention.

FIG. 2 is a flow chart showing the operation of an embodiment of theinvention.

FIG. 3 shows a more detailed diagram of a communications network inwhich embodiments of the invention may be implemented.

FIG. 4 is a block diagram illustrating an embodiment of the operation ofone or more of the servers of the network of FIG. 3.

FIG. 5 is a block diagram showing an embodiment of the operation of oneor more of the clients of the network of FIG. 3.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, the present inventionmay be embodied as a system, method or computer program product.Accordingly, the present invention may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present invention may take the form of a computer program productembodied in any tangible medium of expression having computer usableprogram code embodied in the medium.

Any combination of one or more computer usable or computer readablemedium(s) may be utilized. The computer-usable or computer-readablemedium may be, for example but not limited to, an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system, apparatus,device, or propagation medium. More specific examples (a non-exhaustivelist) of the computer-readable medium would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CDROM), an optical storage device, a transmission media such as thosesupporting the Internet or an intranet, or a magnetic storage device.Note that the computer-usable or computer-readable medium could even bepaper or another suitable medium, upon which the program is printed, asthe program can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory. In the context of this document, a computer-usableor computer-readable medium may be any medium that can contain, store,communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.The computer-usable medium may include a propagated data signal with thecomputer-usable program code embodied therewith, either in baseband oras part of a carrier wave. The computer usable program code may betransmitted using any appropriate medium, including but not limited towireless, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the presentinvention may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava, Smalltalk, C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The program code may execute entirely on the user's computer,partly on the user's computer, as a stand-alone software package, partlyon the user's computer and partly on a remote computer or entirely onthe remote computer or server. In the latter scenario, the remotecomputer may be connected to the user's computer through any type ofnetwork, including a local area network (LAN) or a wide area network(WAN), or the connection may be made to an external computer (forexample, through the Internet using an Internet Service Provider).

The present invention is described below with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products according to embodiments of the invention. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce amachine, such that the instructions, which execute via the processor ofthe computer or other programmable data processing apparatus, createmeans for implementing the functions/acts specified in the flowchartand/or block diagram block or blocks. These computer programinstructions may also be stored in a computer-readable medium that candirect a computer or other programmable data processing apparatus tofunction in a particular manner, such that the instructions stored inthe computer-readable medium produce an article of manufacture includinginstruction means which implement the function/act specified in theflowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide processes for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

The present invention generally relates to messaging applications, suchas text messaging and instant messaging; and more specifically, theinvention relates to user initiated rule based restrictions on the useof messaging applications. As mentioned above, with IM, SMS and othermessaging applications becoming very common, users may receive manyunwanted messages and be bombarded with large numbers of messages, bothof which may be significant problems for the users. Embodiments of thepresent invention effectively address these issues. Generally, this isdone by enabling user initiated rule based restrictions on the use ofmessaging applications.

In one embodiment of the invention, the receiver establishes a set ofrules for the sender that allows the sender a limited number of messagessessions with the receiver. When the sender attempts to send a messageto the receiver, it is determined whether a message session currentlyexists between the sender and the receiver. If a current session exists,the rules set by the receiver are used to determine if the message isallowed to be sent to the receiver. If a session does not currentlyexist, the rules are used to determine whether a new session is allowed.If a new message session is allowed, a new session is established, andthe message is sent to the receiver during the new session.

For example, to restrict or limit instant messaging, a user may be able:

-   -   1. To set user specific restriction rules for chat sessions and        SMS;    -   2. To notify a sender of the number of chat sessions the sender        can have in a particular, defined time frame;    -   3. To identify, detect and trace the number of chat sessions for        a particular user, and to block that user from initiating a new        chat session, if the set threshold is crossed;    -   4. To modify the set threshold at any time; and    -   5. To bypass the count of chat sessions so as to increase the        threshold, if desired.

Also, to restrict or limit SMS, a user may be able:

-   -   1. To set user specific restriction rules for short messages;    -   2. To notify a sender of the number of SMS one can send in a        particular time frame;    -   3. To identify, detect and trace the number of short messages        for a particular user and to block that user from sending short        messages, if the set threshold is crossed;    -   4. To modify the set threshold at any time;    -   5. To bypass the count of short messages so as to increase the        threshold if desired by the receiver.

One embodiment of the invention provides the user (receiver) of aninstant messaging or Short Messaging Service, with the ability to setpredefined rules. The rules that the user can set may include thethreshold chat session value for specific users (senders). Thisthreshold value defines the number of chat sessions the sender can havewith the receiver. This threshold will be for a predefined time frame.This time frame can also be configurable. In one embodiment, the senderwill be informed about the allowed threshold value and will be alertedwhen the number of remaining allowed chat sessions goes below theminimal value set for alert.

When the sender initiates a chat session and sends the first message, itwill be counted as one chat session. Also, in an active chat session,when the users do not communicate with each other for a specifiedtime-out period, then that session will expire. Any new message sentafter that will start up a new session and increment the count towardsthe permissible threshold value. The time-out period can also beconfigurable and user-specific.

The recipient user can also ignore from considering a particular chatsession while taking into account the chat threshold. On the other hand,the receiver can manually end any chat session to increment the count.

Consider the following example:

Consider that there are 2 users: User A and User B.

User B makes the following settings for User A.

Chat session threshold: 10

Time frame for threshold: 1 week

Time-out of chat session: 30 mins.

This means that user A can start at maximum 10 chat sessions with User Bin a time frame of 1 week.

Now, if User A is in an active chat session with User B and if there isno interaction between them for the last 30 minutes, the chat sessionwill expire, which means that a new chat session will be started fromthe next chat message.

Once the restriction is in place, the sender will be informed about itso that the sender can use a messaging session judiciously. Also thesender can configure the system to receive alerts on every session startor when it crosses a minimum threshold. For instance, User A can set theMinimum Alert threshold as 3. So for the last 3 sessions, User A will bealerted with the information about the remaining permissible chatsessions.

User A starts a chat session with B on day 1. The permissible count isdecremented by 1. After the completion of the chat session, the User Ahas another chat session with B after 2 hours lag. This furtherdecrements the count as it is considered as a new chat session becauseof the time-out.

On day 2, the count is 8. User B starts a chat session with A. This doesnot affect the count since the that session is not initiated by A.Later, User A initiates a new chat session. The count goes to 7. Inbetween the chat session, User B needs to take an hour break for lunch.When the chat resumes, User B decides to continue with the chat sessionby selecting to ignore the resumed chat session as a new chat session,and hence the count is not further decremented.

User A has had 7 chat sessions with User B in 5 days. On day 6, whenUser A again initiates a chat session, the system alerts User A thatonly 3 chat sessions are permitted for the next 2 days. User A candecide to continue with the chat session or to cancel it.

The count is again initialized to the predefined value, 10 at the end of7 days.

This will keep the sender aware of the fact that there are a limitednumber of chat sessions permissible, and hence will only initiate amessage session with the receiver, when it is absolutely necessary. Theuser can set different rules for different sets of users.

FIG. 1 depicts an architecture 100 illustrating principles ofembodiments of the invention. This architecture includes a receiver unit102, a sender unit 104, a message server 106, database 110 and softwaremodule 112. In one embodiment of the invention, message sessions areestablished between sender 104 and receiver 102, and messages are sentfrom the sender to the receiver via server 102. The receiver establishesa set of rules for the message sessions and the messages, and theserules are sent to and stored in database 110. When sender 104 attemptsto send a message to receiver 102, the rules are accessed and used, viaserver 106 and software module 110, to determine if the message isallowed to be sent to the receiver.

FIG. 2 illustrates one procedure for implementing an embodiment of theinvention. With reference to FIGS. 1 and 2, at step 202, a set of rulesset by receiver 102 for sender 104 are captured. At step 204, sender 104attempts to send a message; and at step 206, the routine determineswhether a message session is already in progress between the receiverand the sender. If a message session is already in progress, the routineproceeds to step 210, where a check is made to determine if the messagesession has expired due to a time out. If the message session has notexpired due to a time out, the routine moves to step 212 and the messageis sent from the sender to the recipient. If, however, at step 210, themessage session has expired due to a time out, the procedure determines,at step 214, whether the receiver nonetheless allows the old messagesession to continue. If so, the message is sent, at step 212.

At step 214, if the receiver does not allow the message session tocontinue, the routine moves on to step 216. The routine also moves tostep 216 directly from step 206 if at step 206, it is determined that amessage session is not in progress. At step 216, the routine determineswhether a permissible threshold has been crossed. If that threshold hasbeen crossed, then at step 220, the message is blocked and an alert issent to the sender. If, though, at step 216, no permissible thresholdhas been crossed, then the routine moves on to step 222, where it isdetermined if an alert threshold has been crossed. If so, an alert issent to the sender at step 224 and the routine proceeds to step 226. If,at step 222, no alert threshold is crossed, the routine proceedsdirectly to step 226. At this step 226, the number of remainingallowable chat sessions is decremented by one; and then, at step 212,the message is sent from the sender to the recipient.

FIG. 3 shows components of an exemplary environment in which theinvention may be practiced. Not all the components may be required topractice the invention, and variations in the arrangement and type ofthe components may be made without departing from the spirit or scope ofthe invention. As shown, system 300 of FIG. 3 includes local areanetworks (“LANs”)/wide area network 306, wireless network 110, mobiledevices 102-104, client device 105, and application services (AS)308-309.

Generally, mobile devices 302-304 may include virtually any portablecomputing device capable of receiving and sending a message over anetwork, such as networks 306, wireless network 310, and the like, toand from another computing device, another mobile device, and the like.Thus, mobile devices 302-304 may include virtually any portablecomputing device capable of connecting to another computing device andreceiving information. Such devices include portable devices, such ascellular telephones, smart phones, display pagers, radio frequency (RF)devices, infrared (IR) devices, Personal Digital Assistants (PDAs),handheld computers, laptop computers, wearable computers, tabletcomputers, integrated devices combining one or more of the precedingdevices, and the like. As such, mobile devices 302-304 typically rangewidely in terms of capabilities and features. For example, a cell phonemay have a numeric keypad and a few lines of monochrome LCD display onwhich only text may be displayed. In another example, a web-enabledmobile device may have a touch sensitive screen, a stylus, and severallines of color LCD display in which both text and graphics may bedisplayed.

A web-enabled mobile device may include a browser application that isconfigured to receive and to send web pages, web-based messages, and thelike. The browser application may be configured to receive and displaygraphics, text, multimedia, and the like, employing virtually any webbased language, including a wireless application protocol messages(WAP), and the like. In one embodiment, the browser application isenabled to employ Handheld Device Markup Language (HDML), WirelessMarkup Language (WML), WMLScript, JavaScript, Standard GeneralizedMarkup Language (SMGL), HyperText Markup Language (HTML), eXtensibleMarkup Language (XML), and the like, to display and send a message.

Mobile devices 302-304 also may include at least one client applicationthat is configured to receive content from another computing device. Theclient application may include a capability to provide and receivetextual content, graphical content, audio content, and the like. Theclient application may further provide information that identifiesitself, including a type, capability, name, and the like. In oneembodiment, mobile devices 302-304 may uniquely identify themselvesthrough any of a variety of mechanisms, including a phone number, MobileIdentification Number (MIN), an electronic serial number (ESN), MobileSubscriber ISDN (MSISDN), network address, or other device identifier.The information may also indicate a content format that the mobiledevice is enabled to employ. Such information may be provided in amessage, or the like, to other computing devices.

Mobile devices 302-304 may be configured to communicate a message, suchas a text message, using Short Message Service (SMS), Multimedia MessageService (MMS), instant messaging (IM), internet relay chat (IRC),Mardam-Bey's IRC (mIRC), Jabber, and the like, between another computingdevice. However, the present invention is not limited to these messageprotocols, and virtually any other message protocol may be employed.

Mobile devices 302-304 may be further configured to enable a user toparticipate in communications sessions, such as text messaging sessions.As such, mobile devices 302-304 may include a client application that isconfigured to manage various actions on behalf of the client device. Forexample, the client application may enable a user to interact with thebrowser application, email application, IM applications, SMSapplication, and the like.

Mobile devices 302-304 may further be configured to include a clientapplication that enables the end-user to log into an end-user accountthat may be managed by another computing device. Such end-user account,for example, may be configured to enable the end-user to receive emails,send/receive IM messages, SMS messages, access selected web pages, andthe like. Moreover, the end-user account may be further configured toenable the end-user authorization to start an IM session, or othercommunications session, on a mobile device.

Mobile devices 302-304 may each receive messages sent from AS 108-109,from one of the other mobile devices 302-304, or even from anothercomputing device. Mobile devices 302-304 may also send messages to oneof AS 308-309, other mobile devices, or client device 305, or the like.In one embodiment, mobile devices 302-304 may request information to besent to itself, using, for example, text messaging. In anotherembodiment, mobile devices 302-304 may also request that one of AS308-309 send information using, for example, text messaging, to anothermobile device 302-304 (or to client device 305). In one embodiment, therequesting mobile device may be charged a fee to receive the textmessage. In another embodiment, the requesting mobile device may insteadreceive payment for receipt of the text message, such as might arisebased on a promotion, advertisement, or the like. In still anotherembodiment, where the text message is sent to a destination clientdevice, such as one of mobile devices 302-304, or client device 305, thedestination client device might be charged a fee for receiving and/orreading of the text message.

In one embodiment, the requesting mobile device (or client device 305),may be enabled to modify at least a portion of the text message to besent by AS 308-309. For example, a user of the requesting device mightbe able to select, edit, or otherwise, provide at least a portion of thetext message. In one embodiment, however, the user may have no controlon the text message that is to be delivered to a destination clientdevice.

Mobile devices 302-304 may also communicate with non-mobile clientdevices, such as client device 305, or the like. In one embodiment, suchcommunications may include participation in social networkingactivities, receiving and/or sending text messages, or the like. The setof such devices may include devices that typically connect using a wiredcommunications medium such as personal computers, multiprocessorsystems, microprocessor-based or programmable consumer electronics,network PCs, or the like. Similarly, client device 305 may include oneor more applications as described above in conjunction with mobiledevices 302-304. For example, in one embodiment, client device 305 maybe configured to request text messages from AS 308-309, and/or requesttext messages be sent by AS 308-309 to any of mobile devices 302-304, oreven to itself.

Wireless network 310 is configured to couple mobile devices 302-304 andits components with network 306. Wireless network 310 may include any ofa variety of wireless sub-networks that may further overlay stand-alonead-hoc networks, and the like, to provide an infrastructure-orientedconnection for mobile devices 302-304. Such sub-networks may includemesh networks, Wireless LAN (WLAN) networks, cellular networks, and thelike.

Wireless network 310 may further include an autonomous system ofterminals, gateways, routers, and the like connected by wireless radiolinks, and the like. These connectors may be configured to move freelyand randomly and organize themselves arbitrarily, such that the topologyof wireless network 310 may change rapidly.

Wireless network 310 may further employ a plurality of accesstechnologies including, but not limited to 2nd (2G), 3rd (3G), 4th (4G)generation radio access for cellular systems, WLAN, Wireless Router (WR)mesh, and the like. Access technologies such as 2G, 3G, and futureaccess networks may enable wide area coverage for mobile devices, suchas mobile devices 302-304 with various degrees of mobility. For example,wireless network 310 may enable a radio connection through a radionetwork access such as Global System for Mobil communication (GSM),General Packet Radio Services (GPRS), Enhanced Data GSM Environment(EDGE), Wideband Code Division Multiple Access (WCDMA), and the like. Inessence, wireless network 310 may include virtually any wirelesscommunication mechanism by which information may travel between mobiledevices 302-304 and another computing device, network, and the like.

Networks 306 is enabled to employ any form of computer readable mediafor communicating information from one electronic device to another.Also, network 306 can include the Internet in addition to local areanetworks (LANs), wide area networks (WANs), direct connections, such asthrough a universal serial bus (USB) port, other forms ofcomputer-readable media, or any combination thereof. On aninterconnected set of LANs, including those based on differingarchitectures and protocols, a router acts as a link between LANs,enabling messages to be sent from one to another. Also, communicationlinks within LANs typically include twisted wire pair or coaxial cable,while communication links between networks may utilize analog telephonelines, full or fractional dedicated digital lines including T1, T2, T3,and T4, Integrated Services Digital Networks (ISDNs), Digital SubscriberLines (DSLs), wireless links including satellite links, or othercommunications links known to those skilled in the art. Furthermore,remote computers and other related electronic devices could be remotelyconnected to either LANs or WANs via a modem and temporary telephonelink. In essence, network 306 include any communication method by whichinformation may travel between computing devices.

Additionally, communication media typically embodies computer-readableinstructions, data structures, program modules, or other data in amodulated data signal such as a carrier wave, data signal, or othertransport mechanism and includes any information delivery media. Theterms “modulated data signal,” and “carrier-wave signal” includes asignal that has one or more of its characteristics set or changed insuch a manner as to encode information, instructions, data, and thelike, in the signal. By way of example, communication media includeswired media such as twisted pair, coaxial cable, fiber optics, waveguides, and other wired media and wireless media such as acoustic, RF,infrared, and other wireless media.

AS 308-309 includes virtually any device that may be configured toprovide an application service. Such application services or simplyapplications include, but are not limited to, email applications, searchapplications, video applications, audio applications, graphicapplications, social networking applications, text message applications,or the like. In one embodiment, AS 308-309 may operate as a web server.However, AS 308-309 are not limited to web servers, and may also operateas a messaging server, a File Transfer Protocol (FTP) server, a databaseserver, a content server, or the like, in which to provide anapplication. Additionally, each of AS 308-309 may be configured toperform a different operation. Thus, for example, AS 308 may beconfigured as a messaging server, while AS 309 is configured as adatabase server, social networking server, or the like. However, AS308-309 may each be configured to communicate using text messages.Devices that may operate as AS 308-309 include personal computersdesktop computers, multiprocessor systems, microprocessor-based orprogrammable consumer electronics, network PCs, servers, and the like.

AS 308-309 may be configured to initiate a message to be sent to one ofclient devices 302-305. Such messages may include, for example, analert, an advertisement, a relayed message, a news message, or the like.In one embodiment, AS 308-309 may also respond to a request to performsome action, from one of client devices 302-305, or even anothercomputing device. For example, in one embodiment, AS 308-309 may receivea request to send a message, an alert, an advertisement, or the like, toone or more of client devices 302-305. However, AS 308-309 are notlimited to sending a message based on a request from another device.Thus, for example, AS 308-309 may also initiate sending of a textmessage to a computing device, based on an internal action, condition,or the like, including for example, promoting a new product, a newservice, sending of an advertisement, or the like.

AS 308-309 may receive from a computing device a message asking that amessage be sent to the requesting device's device identifier. AS308-309, may also receive or otherwise determine, a user identifier,user account, or the like, associated with the requesting device. In oneembodiment, AS 308-309 may also receive a destination device's deviceidentifier. In one embodiment, AS 308-309 may be configured to charge afee for sending the text message. In one embodiment, the fee might becharged to the requesting device, requesting user, or the like. Inanother embodiment, the fee might be charged to the destination device.However, a fee might also be charged to both the requesting device andto the destination device. In still another embodiment, the requestingand/or destination device may also receive a reward, such as payment, adiscount, or the like, for messages received.

Referring to FIG. 4, a block diagram depicts a data processing systemthat may be implemented as a server, such as server 398 or 309 in FIG.3, in accordance with an embodiment of the present invention. Dataprocessing system 400 may be a symmetric multiprocessor (SMP) systemincluding a plurality of processors 402 and 404 connected to system bus406. Alternatively, a single processor system may be employed. Alsoconnected to system bus 406 is memory controller/cache 408, whichprovides an interface to local memory 409. I/O bus bridge 410 isconnected to system bus 406 and provides an interface to I/O bus 412.Memory controller/cache 408 and I/O bus bridge 410 may be integrated asdepicted.

Peripheral component interconnect (PCI) bus bridge 414 connected to I/Obus 412 provides an interface to PCI local bus 416. A number of modems418-420 may be connected to PCI bus 416. Typical PCI bus implementationssupport four PCI expansion slots or add-in connectors. Communicationslinks to network computers, such as clients 302, 303, 304 and 305 inFIG. 3, may be provided through modem 418 and network adapter 420connected to PCI local bus 416 through add-in boards. Additional PCI busbridges 422 and 424 provide interfaces for additional PCI buses 426 and428, from which additional modems or network adapters may be supported.In this manner, server 400 allows connections to multiple networkcomputers. A memory-mapped graphics adapter 430 and hard disk 432 mayalso be connected to I/O bus 412 as depicted, either directly orindirectly.

Those of ordinary skill in the art will appreciate that the hardwaredepicted in FIG. 4 may vary. For example, other peripheral devices, suchas optical disk drives and the like, also may be used in addition or inplace of the hardware depicted. The depicted example is not meant toimply architectural limitations with respect to the present invention.The data processing system depicted in FIG. 4 may be, for example, anIBM RISC/System 6000, a product of International Business MachinesCorporation in Armonk, N.Y., running the Advanced Interactive Executive(AIX) operating system.

FIG. 5 shows a general purpose information system 500 that can be usedin client devices 301, 302, 303. Information system 500 includes aprocessor 505. Bus 210 couples processor 505 to system memory 515 andvideo graphics controller 520. A display 525 couples to video graphicscontroller 520. Nonvolatile storage 530, such as a hard disk drive, CDdrive, DVD drive, or other nonvolatile storage couples to bus 510 toprovide system 200 with permanent storage of information. An operatingsystem 535 loads in memory 515 to govern the operation of system 500.I/O devices 520, such as a keyboard, couple to bus 510. One or moreexpansion busses 545, such as USB, IEEE 1394 bus, ATA, SATA, PCI, PCIEand other busses, couple to bus 510 to facilitate the connection ofperipherals and devices to system 500. A network adapter 550 couples tobus 510 to enable system 500 to connect by wire or wirelessly to networkinfrastructures such as network infrastructure shown in FIG. 3.

System 500 loads application software 555 from nonvolatile storage 530to memory 515 for execution. The particular application software 555loaded into memory 515 of system 500 determines the operationalcharacteristics of system 500. System 500 is configurable as clientdevices 301, 302, 303. When system 500 acts as client devices 301, 302,303 with instant messaging, system 500 loads an IM client application525 into system memory 515.

While it is apparent that the invention herein disclosed is wellcalculated to fulfill the objectives discussed above, it will beappreciated that numerous modifications and embodiments may be devisedby those skilled in the art, and it is intended that the appended claimscover all such modifications and embodiments as fall within the truespirit and scope of the present invention.

The invention claimed is:
 1. A method of implementing user initiatedrule based restrictions on the use of messaging applications, whereinmessage sessions are established between a pre-specified one sender anda receiver, and during each of the message sessions, one or moremessages are sent from the pre-specified one sender to the receiver, themethod comprising: the receiver establishing a set of specified rulesfor the pre-specified one sender, said set of rules including a limit onthe number of message sessions the pre-specified one sender is allowedto establish with the receiver during a defined time period; thepre-specified one sender attempting to initiate a new message sessionwith the receiver; determining, based on said set of rules and by usingone or more processing units executing a messaging access program,whether a new message session is allowed to be established between thepre-identified one sender and the receiver, including determiningwhether a number of message sessions established between thepre-identified one sender and the receiver during said defined timeperiod is less than the number of message sessions the pre-identifiedone sender is allowed to establish with the receiver during the definedtime period; if the number of message sessions established between thepre-identified one sender and the receiver during said defined timeperiod is less than the number of message sessions that thepre-specified one sender is allowed to establish with the receiverduring said defined time period, establishing the new message sessionbetween the pre-specified one sender and the receiver; and the receivermodifying the set of specified rules based on specified actions of thesender.
 2. The method according to claim 1, wherein the receivermodifying the set of specified rules includes the receiver modifying thenumber of message sessions the pre-identified one sender is allowed toinitiate with the receiver during the defined time period.
 3. The methodaccording to claim 1, wherein the receiver modifying the set ofspecified rules includes the receiver modifying a number of messages thepre-identified one sender is allowed to send to the receiver during oneof the message sessions.
 4. The method according to claim 1, wherein thereceiver modifying the set of specified rules includes the receivermodifying a length of the defined time period.
 5. The method accordingto claim 4, wherein said determining if the new message session isallowed includes determining whether a message session currently existsbetween the pre-identified one sender and the receiver.
 6. The methodaccording to claim 1, further comprising notifying the sender of thenumber of message sessions the sender is allowed to establish with thereceiver during the defined time period.
 7. The method according toclaim 1, further comprising when the number of message sessions that thepre-identified one sender is allowed to establish with the receiver hasbeen reached, alerting the sender that said number has been reached. 8.The method according to claim 1, wherein the establishing a set of rulesincludes setting an alert threshold number of message sessions below thenumber of message sessions the specified one sender is allowed toestablish with the receiver during the defined time period.
 9. Themethod according to claim 8, further comprising when said alertthreshold number of message sessions has been reached, alerting thespecified one sender that said alert threshold number has been reached.10. The method according to claim 1, wherein the determining, based onsaid set of rules and by using one or more processing units executing amessaging access program, whether a new message session is allowed:keeping a count of the number of message sessions established betweenthe specified one sender and the receiver during said defined timeperiod; and not including in said count selected ones of the messagesessions established between the specified one sender and the receiver.11. A system for implementing user initiated rule based restrictions onthe use of messaging applications, wherein message sessions areestablished between a pre-specified one sender and a receiver, andduring each of the message sessions, one or more messages are sent fromthe pre-specified one sender to the receiver, the system comprising: areceiver communications device for establishing and modifying a set ofspecified rules for the pre-specified one sender, said set of rulesincluding a limit on the number of message sessions the pre-specifiedone sender is allowed to establish with the receiver communicationsdevice during a defined time period; a memory storage device for storingthe set of rules; a pre-specified one sender communications device forattempting to initiate a new message session with the receivercommunications device; and one or more processor units includinginstructions for: receiving from the receiver communications device theset of specified rules; receiving input from the receiver communicationsdevice for modifying the set of specified rules based on specifiedactions of the sender communications device; determining, based on saidset of rules, whether a new message session is allowed to be establishedbetween the pre-identified one sender communications device and thereceiver communications device, including determining whether a numberof message sessions established between the pre-identified one sendercommunications device and the receiver communications device during saiddefined time period is less than the number of message sessions thepre-identified one sender communications device is allowed to establishwith the receiver communications device during the defined time period;and if the number of message sessions established between thepre-identified one sender communications device and the receivercommunications device during said defined time period is less than thenumber of message sessions that the pre-specified one sendercommunications device is allowed to establish with the receivercommunications device during said defined time period, establishing thenew message session between the pre-specified one sender communicationsdevice and the receiver communications device.
 12. The system accordingto claim 11, wherein the receiver unit communications device modifiesthe number of message sessions the pre-specified one sendercommunications device is allowed to initiate with the receivercommunications device during the defined time period.
 13. The systemaccording to claim 11, wherein the receiver communications devicemodifies a number of messages the pre-specified one sendercommunications device is allowed to send to the receiver communicationsdevice during one of the message sessions.
 14. The system according toclaim 11, wherein the receiver communications device modifies a lengthof the defined time period.
 15. The system according to claim 11,wherein said determining if the new message session is allowed includesdetermining whether a message session currently exists between theidentified one sender communications device and the receivercommunications device.
 16. An article of manufacture comprising: atleast one tangible computer readable device having computer readableprogram code logic tangibly embodied therein to execute machineinstructions in one or more processing units for implementing userinitiated rule-based restrictions on a messaging application in acommunication network, wherein message sessions are established betweena pre-specified one sender and a receiver and during each of the messagesessions, one or more messages are sent from the pre-specified onesender to the receiver, said computer readable program code logic, whenexecuting, performing the following: receiving a set of specified rulesfor the pre-specified one sender, said set of rules including a limit onthe number of message sessions the pre-specified one sender is allowedto establish with the receiver during a defined time period; when thepre-specified one sender attempts to initiate a new message session withthe receiver, determining, based on said set of rules, whether a newmessage session is allowed to be established between the pre-identifiedone sender and the receiver, including determining whether a number ofmessage sessions established between the pre-identified one sender andthe receiver during said defined time period is less than the number ofmessage sessions the pre-identified one sender is allowed to establishwith the receiver during the defined time period; if the number ofmessage sessions established between the pre-identified one sender andthe receiver during said defined time period is less than the number ofmessage sessions that the pre-specified one sender is allowed toestablish with the receiver during said defined time period,establishing the new message session between the pre-specified onesender and the receiver; and receiving input from the receiver formodifying the set of specified rules based on specified actions of thesender.
 17. The article of manufacture according to claim 16, whereinthe receiving input from the receiver includes receiving input formodifying the number of message sessions the pre-identified one senderis allowed to initiate with the receiver during the defined time period.18. The article of manufacture according to claim 16, wherein thereceiving input from the receiver includes receiving input for modifyinga number of messages the pre-identified one sender is allowed to send tothe receiver during one of the message sessions.
 19. The article ofmanufacture according to claim 16, wherein the receiving input from thereceiver includes receiving input for modifying a length of the definedtime period.
 20. The article of manufacture according to claim 16,wherein said determining if the new message session is allowed includesdetermining whether a message session currently exists between thepre-identified one sender and the receiver.